Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0496

reference
160-tree-1
name
0496
tree-preservation-order

undefined

160-tpo-1
uprn
address-text
point
POINT (-1.005329 50.854035)
geometry
MULTIPOLYGON (((-1.005258 50.854027,-1.005261 50.854041,-1.005271 50.854054,-1.005286 50.854064,-1.005306 50.854070,-1.005328 50.854073,-1.005350 50.854071,-1.005370 50.854065,-1.005386 50.854055,-1.005396 50.854042,-1.005400 50.854028,-1.005397 50.854014,-1.005387 50.854002,-1.005371 50.853992,-1.005352 50.853985,-1.005330 50.853983,-1.005308 50.853985,-1.005288 50.853991,-1.005272 50.854001,-1.005262 50.854013,-1.005258 50.854027)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL